Enable https frontend support - #43
Merged
Merged
Conversation
Signed-off-by: Karl Hepworth <3070264+fubarhouse@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This work enables HAProxy to be served on port 443 (HTTPS).
It's now a reality as part of downstream pygmy support, or rather, a simpler UX to enable HTTPS.
This also features an automated way to disable the inclusion of the certificate and will prevent the installation of the default certificate. Pygmy itself will mount the certificate on container creation if it's configured to do so, which will enable this.
The only caveat is that the certificate must be valid for the root domain, which will if unsuccessful still happily serve on port 80.